Below you can find the config output (I changed domain settings: BaseDN, BindDN, BindPassword and ServerHost): { "AccessControl": { "AccessControlRulesProcessingEnabled": "false", "AccessRestrictedToUserGroups": "false", "AuthorizedUserGroups": [ ], "DomainGroupsEnabled": true, "UserGroupsBackend": "{6f0a491e-c1c6-4338-8244-f823b0bf8670}" }, "Authentication": { "Method": 0, "PrivateKeyBaseDir": "%GLOBALAPPDATA%\keys\private", "PublicKeyBaseDir": "%GLOBALAPPDATA%\keys\public" }, "BuiltinDirectory": { "NetworkObjects": { "JsonStoreArray": [ ] } }, "Core": { "InstallationID": "dfa175a6-76ee-4967-8d40-eb4d56737502", "PluginVersions": { "JsonStoreObject": { "{14bacaaa-ebe5-449c-b881-5b382f952571}": "1.1", "{1b08265b-348f-4978-acaa-45d4f6b90bd9}": "1.1", "{1baa01e0-02d6-4494-a766-788f5b225991}": "1.1", "{1bdb0d1c-f8eb-4d21-a093-d555a10f3975}": "1.1", "{2917cdeb-ac13-4099-8715-20368254a367}": "1.1", "{2ad98ccb-e9a5-43ef-8c4c-876ac5efbcb1}": "1.1", "{387a0c43-1355-4ff6-9e1f-d098e9ce5127}": "1.1", "{39d7a07f-94db-4912-aa1a-c4df8aee3879}": "1.1", "{4122e8ca-b617-4e36-b851-8e050ed2d82e}": "1.1", "{4790bad8-4c56-40d5-8361-099a68f0c24b}": "1.1", "{67dfc1c1-8f37-4539-a298-16e74e34fd8b}": "1.1", "{6f0a491e-c1c6-4338-8244-f823b0bf8670}": "1.1", "{85f6c631-e75a-4c78-8cb2-a7f3f502015a}": "1.1", "{8ae6668b-9c12-4b29-9bfc-ff89f6604164}": "1.1", "{a54ee018-42bf-4569-90c7-0d8470125ccf}": "1.1", "{b47bcae0-24ff-4bf5-869c-484d64af5c4c}": "1.1", "{ee322521-f4fb-482d-b082-82a79003afa7}": "1.1" } } }, "Demo": { "FramebufferUpdateInterval": "100", "KeyFrameInterval": "10", "MemoryLimit": "128" }, "Directories": { "Screenshots": "%APPDATA%\Screenshots", "UserConfiguration": "%APPDATA%\Config" }, "ExternalVncServer": { "ServerPort": "5900" }, "LDAP": { "BaseDN": "DC=mydomain,DC=local", "BindDN": "mydomain\Veyon", "BindPassword": "passwordxxx", "ComputerGroupTree": "", "ComputerHostNameAsFQDN": "false", "ComputerHostNameAttribute": "cn", "ComputerRoomMembersByContainer": "true", "ComputerTree": "OU=PcLokalen", "GroupMemberAttribute": "memberOf", "GroupTree": "OU=Leerkrachten", "QueryNamingContext": "false", "RecursiveSearchOperations": "true", "ServerHost": "mydomain.local", "ServerPort": "389", "UseBindCredentials": "true", "UserLoginAttribute": "sAMAccountName", "UserTree": "OU=Leerkrachten" }, "Logging": { "LogFileDirectory": "$TEMP", "LogFileRotationCount": 10, "LogFileRotationEnabled": false, "LogFileSizeLimit": 100, "LogFileSizeLimitEnabled": false, "LogLevel": 4, "LogToStdErr": true, "LogToSystem": false }, "Master": { "ComputerMonitoringBackgroundColor": "#ffffff", "ComputerMonitoringUpdateInterval": 1000 }, "Network": { "DemoServerPort": 11400, "FeatureWorkerManagerPort": 11300, "FirewallExceptionEnabled": "1", "PrimaryServicePort": 11100, "VncServerPort": 11200 }, "NetworkObjectDirectory": { "UpdateInterval": 60 }, "Service": { "Autostart": true, "FailedAuthenticationNotifications": true, "HideTrayIcon": "true", "RemoteConnectionNotifications": false, "SoftwareSASEnabled": "1" }, "UI": { "ApplicationName": "", "Language": "English - American English (en_US)" }, "UltraVNC": { "CaptureLayeredWindows": "true", "Configured": "true", "LowAccuracy": "true", "PollFullScreen": "true" } }

Yes, there's a configuration: "Disable the Swipe Feature of Windows 10" For Windows 10 users with a touch-enabled device, it is possible to enter Task View by swiping left from the edge of the screen. To stop this from happening, you can disable this swipe feature by Windows group policy: Computer Configuration > Administrative Templates > Windows Components > Edge UI ("Rand-UI" in German versions)

Using Linuxmint 19 Tara and XFCE desktop. I don't know what to examine but I uploaded the log files in my google drive, here is the link to it. veyon_logs.zip

Welcome to Veyon! First of all please consult our troubleshooting guide at https://docs.veyon.io/en/latest/admin/troubleshooting.html Can you see thumbnails of the clients in Veyon Master?

I suspect there's an issue with the new desktop duplication engine. You can try to stop the service, remove ddengine.dll / ddengine64.dll and restart the computer. Are you able to see the second screen of this client afterwards?

Hi, Sorry, I was too busy to go back to veyon install this last days. Coming back to it, today, I fixed my "problem" : In fact, my .json file was malformed. But, as veyon-ctl returned "OK" message whan I imported it, I didn't suspect that. Now, I fixed it, and it works well. For the record, I have no problem generating UUID with python or even bash, using the following commands : # bash : uuid=$(uuidgen) # python : import uuid newUid = "{" + str(uuid.uuid4()) + "}" I have now a working veyon installation for all my rooms. Every new PC automatically sends its informations to veyon conf (ip, Mac, hostname, UUID and room). Thank you for your help and your great job developping veyon. It's a powerful and really usefull software for education.

This is indeed an insufficiency in the import command. I just added the missing support for importing an optional object type column. It will be part of Veyon 4.2 and maybe we'll also backport it to future 4.1 releases.

Hello Martin, making all features in Veyon Master accessible through the command line as well is one of our long-term goals. Until then the only thing you can try is to modify the source code such that specific hotkeys are assigned to buttons in the toolbar. I can offer commercial services to get this done for you - please write an email to support@veyon.io. Best regards Tobias

Please check the permissions on the key files in /etc/veyon/keys/* - you can change the group allowed to read the private key easily using Veyon Configurator -> Authentication keys -> Set access group

Welcome to Veyon! Have you already read http://docs.veyon.io/en/latest/admin/configuration.html#authentication ? It explains the basics concerning authentication methods. You have to switch the method from logon to keyfile authentication if you want to use it (http://docs.veyon.io/en/latest/admin/reference.html#authentication). If not, you have to make sure to have identical accounts on all computers so you use your normal teacher account for Veyon Master logon.

Yes please open a bug report so we can deal with that issue in detail.

Welcome to Veyon! If the machines are greyed out they can't be reached by the Master at all. If computers are shown in red they are reachable via ping but not the Veyon Service i.e. no service running or authentication problems. Did you follow the troubleshooting instructions at http://docs.veyon.io/en/latest/admin/troubleshooting.html#computers-can-t-be-accessed ?

Uninstalling and rebooting should help

Thank you for your feedback! We recently improved this in the current development branch so this will be fixed in 4.2. The full name will be displayed properly. May be we'll also backport the change to 4.1.x.

@fred Sorry for the late answer. I was on vacation the last days. Yes that´s it. The Veyon Master should be able to lock or unlock a Computer (Veyon Client) without being able to see what the connected user ist doing.

Okidoki. => https://github.com/veyon/veyon/issues/448

Hi again, I slept on it, as one says, and I realized there was no problem with UIDs : I just got to generate and include them in the conf. Very often, network based softwares work with agents on clients, that sends its information on server, to be "recognized". I realised there is no such process in veyon, and that a computer's UID is only present on master, the client doesn't even know it. Sorry for that "stupid" question. You can mark as "resolved" For the record : I'm discovering Veyon, and I'm really impressed by its possibilities and its fast evolution. Thanks for your great job E.T.

Does Wake-on-LAN work in general on your computers, i.e. enabled in BIOS / NIC setup? Have you already tried a separate Wake-on-LAN tool? Can you try to disable your firewall temporarily?

Yes I double checked that. I also telnet the port and its not active thats how I concluded it was blocked. Is there another port that it might work on or is that the only port the service runs on?

@tobydox I just updated to version 4.1.4. indeed the problem was solved. Thank you!!